Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix OS Discovery Tool Windows for Nvidia GPU detection #53

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

lbertini
Copy link

Description:
This pull request addresses an issue in the PowerShell script for detecting NVIDIA GPU drivers and their modes (Graphics or Compute). The current script "getWindowsOsInvToIntersight.ps1" has an error with the nvidia-smi command that prevents it from executing correctly in a remote PowerShell context.

Issue Resolved
Fixed the error where when a GPU (NVIDIA A100 in my lab) was unable to identify the model (TCC or WDDM) and a null value was being registered in the key. Due to this, the HCL part of Intersight was not being populated.

What was changed

  • Corrected Command Construction: Removed single quotes around the path to nvidia-smi.exe when constructing the command string. Proper escaping is applied to handle spaces in paths. Also "no header" was changed to "noheader".

  • Fixed Command Execution with Invoke-Expression: Modified how the nvidia-smi command is executed using Invoke-Expression to ensure it runs correctly in a remote session via Invoke-Command.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant